Component documentationDIMONA Declarations

 

In Belgium, employers are legally obliged to report immediately the starting and/or ending of the contractual relationship between themselves and the employees.

DIMONA (“Déclaration IMmédiate/ONmiddellijke Aangifte”) refers to the electronic reporting system that enables employee movements (hiring, changes, and departures) to be reported to the National Office for Social Security (NOSS). The reporting of employees’ entries and leavings is done with DIMONA declarations.

The following declaration types cover the different actions and organizational assignments that can be applied to an employee:

Declaration Type

Action Type

IN

For newly (re)hired employees

OUT

For employees who are leaving the company

UPDATE

Only applicable if the hiring or leaving date for the employee has been changed, and if this change occurs before the initially reported date.

CANCEL

Applies to those employees who do not attend their start date of employment and for whom a DIMONA IN declaration has been made.

Depending on the business requirements of a company, the Belgian localization supports different scenarios to collect the reporting data and exchange this data with the administration.

Each DIMONA scenario consists of the following steps:

  1. Selecting data to start the declaration

  2. Collecting data

  3. Sending data

  4. Handling a receipt message

  5. Finalizing the process with a notification

Declarations can be generated either manually (no file is created) or electronically (a file is created).

Implementation Considerations

As of October 1, 2010, electronic declarations must be submitted in XML format. The flat file format previously used for electronic DIMONA declarations is not longer accepted. To generate DIMONA declarations using XML files, you have to convert historical DIMONA declaration data first.

The historical data is converted and updated using the Dimona Declaration: Prepare Reference Data (RPCDIUB0) report. You can access the report in Customizing for Payroll: Belgium, under Start of the navigation path Social Insurance Next navigation step Dimona Declaration (valid 2010) Next navigation step Prepare Master Data for New Dimona (Data Conversion) Next navigation step Prepare Reference Data End of the navigation path.

Note Note

As of October 1, 2010, declaration forms that contain duplicate or overlapping declaration records are rejected by the National Office for Social Security (RSZ/ONSS). You carry out the relevant activities related to duplicate prevention in Customizing for Payroll: Belgium, under Start of the navigation path Social Insurance Next navigation step Dimona Declaration (valid 2010) Next navigation step Duplicate Prevention End of the navigation path.

It is the employer’s responsibility to prevent reporting duplicate and overlapping occupation periods. When duplicate or overlapping occupation periods are reported, the Belgian authorities notify the employer via the notification file and the declaration is rejected.

End of the note.

Features

Occupation Period

To assist with duplicate prevention, an occupation period has been introduced to the Dimona Declarations (Infotype 0735) infotype to uniquely identify the period during which an occupational relationship exists between an employer and employee. An occupation period is defined by the following functional key values for the employer, employee, and the employment type:

  • Social insurance number for the employer

  • Social insurance number for the employee, commonly referred to as INSS number

  • Employment type: contract start date and time, contract end date and time, joint commission, sub-entity number (relevant only for public sector), and interim user company ID.

The combination of key elements results in a unique occupation period. However, a change of the starting date (after the declaration has been accepted) from a DIMONA master record (that is, when it already has a duplicate record) is not supported by SAP.

DIMONA Statuses

To reflect the processing and submission progress, DIMONA declarations are assigned different statuses. The status can apply at two levels, as follows:

  • To the declaration file, in which case it can apply to multiple employee declarations.

  • To the declaration form, that is, a declaration for an individual employee once processing has begun.

The statuses applied to a declaration, which are available in the Dimona Declaration (0735) infotype, depend on whether the declaration is generated manually or electronically:

  • The status for manually reported declarations is immediately received and can therefore be immediately recorded in the Dimona Declaration (0735) infotype.

  • The status for electronically reported declarations is handled using the B2A Manager (H99_B2AMANAGER) and the Status Handler Viewer (RPDHDL9S). The form reference ID links the status of the employee’s declaration in the Status Handler to the displayed status in the Dimona Declaration (0735) infotype. For more information about the communication with authorities, see Communication with Authorities: B2A Manager and Status Handler.

DIMONA Files

There is a number of files involved in the DIMONA declaration process, and therefore involved in the exchange of data between the employer and the RSZ/ONSS.

These files receive unique identifiers for ongoing reference. Every time that the files are handled or processed, it is regarding these unique identifiers.

The handling of the files results in changes to the declaration status of DIMONA declaration records, saved in the Dimona Declaration (0735) infotype.

Note that the sender is not always the same as the employer.

DIMONA files include the following:

  • Declaration File

    Sent by the employer (or by a service provider acting as the sender). It declares the period in which a relationship between the employer and an employee exists. DIMONA declaration files can include more than one declaration form. That means that aDIMONA declaration file can contain either multiple declarations (for multiple employees) or it can be created for a single employee (per employee). The option to include one or many DIMONA declaration forms in a declaration file is determined by the File generation mode field on the selection screen of the Dimona Declaration: Generation (RPCDIGB0) report.

    Declaration files are automatically assigned a file name, according to the file naming convention specified by the RSZ/ONSS.

  • Receipt File

    Informs the employer (sender) about the technical receipt status of the DIMONA declaration file.

    If the DIMONA declaration file could not be received (for example, if there is an error in the file naming convention or an error in the XML tags), then the file is not handled and the complete file is rejected. If this occurs, the receipt file lists the technical errors. In all cases (including rejection), the file is assigned a number that uniquely identifies the file.

  • Notification File

    Informs the employer (sender) about the functional declaration status of the DIMONA declaration file.

    The declaration status can be either positive (accepted), negative (rejected), or to be validated (pending a response).

    Files are rejected if they contain duplicate or overlapping occupation periods. Like the declaration files, notification files can contain more than one declaration. If a notification file contains multiple declarations, all the declarations have been initially reported with the same DIMONA declaration file.

    Anomalies associated with a notification file can be investigated using the SI Notification Viewer (RPUNOVB0).

Note Note

There is no file that is specifically used for DIMONA corrections. Corrections are managed via declarations of the type update (Dimona UPDATE). This approach is different to the handling of corrections for DmfA Declarations.

End of the note.